New check to validate if build was replaced by a newer one #815
Merged
Conversation
dpaulson45
force-pushed
the
dpaul-KnownIssues
branch
from
dfdc4ab to
d202ad6
Compare
Created a shared function that can get the extracted information of functions from files and return a string that you can then run Invoke-Expression against.
Added main pester testing logic to make sure that we are on the correct build and everything or not for a fix.
This reverts commit f6c801c.
lusassl-msft
approved these changes
Dec 21, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Added some additional logic in the Analyzer Engine to determine if the Exchange build number is running into a known issue and if we have a fix for that build.
Replacing PR #812